Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
495-tree-1
name
1600
tree-preservation-order

undefined

495-tpo-1
uprn
address-text
point
POINT (-1.036736 50.886771)
geometry
MULTIPOLYGON (((-1.036651 50.886762,-1.036655 50.886779,-1.036666 50.886794,-1.036685 50.886806,-1.036709 50.886814,-1.036735 50.886817,-1.036761 50.886814,-1.036785 50.886807,-1.036804 50.886795,-1.036817 50.886780,-1.036821 50.886764,-1.036818 50.886747,-1.036806 50.886732,-1.036787 50.886720,-1.036763 50.886712,-1.036737 50.886709,-1.036711 50.886711,-1.036687 50.886719,-1.036668 50.886731,-1.036655 50.886746,-1.036651 50.886762)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL